-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: limit amount of workers on CI #2014
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit d4715ff. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 5 targets
Sent with 💌 from NxCloud. |
00da7d5
to
9ae6b7c
Compare
BundleMonUnchanged files (3)
No change in files bundle size Unchanged groups (3)
Final result: ✅ View report in BundleMon website ➡️ |
9ae6b7c
to
5dc7c4e
Compare
BundleMon (NGXS Plugins)Unchanged files (14)
No change in files bundle size Unchanged groups (3)
Final result: ✅ View report in BundleMon website ➡️ |
BundleMon (Integration Projects)Unchanged files (3)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
b1394d9
to
49a47af
Compare
49a47af
to
d4715ff
Compare
Code Climate has analyzed commit d4715ff and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 96.7% (0.0% change). View more on Code Climate. |
It looks like on CircleCI unit tests task throws due to memory issues https://discuss.circleci.com/t/jest-unit-test-works-locally-but-fail-on-circleci-docker-image-cimg-node-16-13/42620/2
I was able to get the error code 137 by running
yarn jest -c packages/store/jest.config.js
. I guess because node just kills the process Nx is not able to handle the exit properly